Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix data101 image, update readme/contributing #1

Merged
merged 6 commits into from
Sep 5, 2024

Conversation

shaneknapp
Copy link
Contributor

@shaneknapp shaneknapp commented Sep 5, 2024

this builds locally, but was failing here. why!?!?

plan A was to tweak the readmes just to trigger an image build.

plan B was to fix the image after banging on it for the past 3 hours.

i did not want plan B. just A.

@shaneknapp shaneknapp changed the title update readme and trigger a build Fix data101 image, update readme/contributing Sep 5, 2024
@shaneknapp
Copy link
Contributor Author

shaneknapp commented Sep 5, 2024

building locally, i successfully install environment.yml:

Step 40/55 : RUN TIMEFORMAT='time: %3R' bash -c 'time ${MAMBA_EXE} env update -p ${NB_PYTHON_PREFIX} --file "environment.yml" && time ${MAMBA_EXE} clean --all -f -y && ${MAMBA_EXE} list -p ${NB_PYTHON_PREFIX} '
 ---> Running in b38f50e7f211
Channels:
 - conda-forge
 - defaults
Platform: linux-64
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... done


==> WARNING: A newer version of conda exists. <==
    current version: 24.3.0
    latest version: 24.7.1

Please update conda by running

    $ conda update -n base -c conda-forge conda



Downloading and Extracting Packages: ...working... done
Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... 
Downloading and Extracting Packages: ...working... done
Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working...

done

here, however, it's failing w/a massive dep hell:

 Step 40/55 : RUN TIMEFORMAT='time: %3R' bash -c 'time $***MAMBA_EXE*** env update -p $***NB_PYTHON_PREFIX*** --file "environment.yml" && time $***MAMBA_EXE*** clean --all -f -y && $***MAMBA_EXE*** list -p $***NB_PYTHON_PREFIX*** '
   ---> Running in 255a9a2f6c0d
  Channels:
   - conda-forge
  Platform: linux-64
  Collecting package metadata (repodata.json): ...working... done
  Solving environment: ...working... failed
  Channels:
   - conda-forge
  Platform: linux-64
  Collecting package metadata (repodata.json): ...working... done
  Solving environment: ...working... failed
  
  LibMambaUnsatisfiableError: Encountered problems while solving:
    - package pytest-7.1.2-py310hff52083_0 requires python_abi 3.10.* *_cp310, but none of the providers can be installed
    - package pillow-9.2.0-py311h50def17_4 requires python_abi 3.11.* *_cp311, but none of the providers can be installed
  
  Could not solve for environment specs
  The following packages are incompatible
  ├─ coverage 7.2.2  is installable with the potential options
  │  ├─ coverage 7.2.2 would require
  │  │  └─ python >=3.10,<3.11.0a0  with the potential options
  │  │     ├─ python [3.10.14|3.11.8|...|3.9.19] would require
  │  │     │  └─ openssl >=3.2.1,<4.0a0 , which can be installed;
  │  │     ├─ python [3.10.7|3.10.8|3.11.0|3.9.14|3.9.15] would require
  │  │     │  └─ openssl >=1.1.1s,<1.1.2a , which conflicts with any installable versions previously reported;
  │  │     ├─ python [3.10.10|3.10.11|3.11.1|3.11.2|3.11.3] would require
  │  │     │  └─ openssl >=3.1.0,<4.0a0  with the potential options
  │  │     │     ├─ openssl [3.3.1|3.3.2], which can be installed;

...and another 1k+ lines

@shaneknapp
Copy link
Contributor Author

shaneknapp commented Sep 5, 2024

ok, it looks like it's passing now... i did have to upgrade/pin the following packages to get it to build, however:

- pillow==10.0.1 # sknapp 2024-09-05 had to unpin this version to fix build ==9.2.0
- pytest==8.3.2 # sknapp 2024-09-05 had to unpin this version to fix build ==7.1.2
- sympy==1.13.2 # sknapp 2024-09-05 had to unpin this version to fix build ==1.10.1

we can test this when we deploy to staging.

@shaneknapp shaneknapp merged commit f702848 into berkeley-dsep-infra:main Sep 5, 2024
2 checks passed
@shaneknapp shaneknapp deleted the trigger-image-build branch September 5, 2024 22:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant